home *** CD-ROM | disk | FTP | other *** search
- .TOPIC:
- Multinet
-
- VBBS 6.12 Documentation --9-B-1
-
- ╔════════════════════════════════════════╗
- ║ CHAPTER 9 ANNEX B MULTINET ║
- ╚════════════════════════════════════════╝
-
- The Multinetwork Master List
- ════════════════════════════
- The master list of allowable networks is a file named
- NETWORKS.LST, and is located in the VBBS 'Data' subdirectory.
-
- This master list is the only way for VBBS to identify the origin
- and destination of posts and e-mail, so it is a requirement
- that major networks be listed in the NETWORKS.LST file.
-
- The NETWORKS.LST file is an ascii file in following format:
-
- 1,1,VirtualNET
- 2,2,WWIVnet
- 3,2,WWIVLink
- 4,4,FIDOnet
- 5,3,USEnet
-
- The NETWORKID comes first, followed by the NETWORKTYPE,
- and finally, the NETWORKNAME.
-
- To view the network entries in the NETWORKS.LST file, simply
- choose option 7, Network Configuration, on the VConfig menu.
-
- The Multinet Mail Tosser
- ═══════════════════════
- The multinet mail tosser is built directly into VBBS.
- No external mail tossers from third parties are needed,
- although VBBS can be configured to use them if desired.
-
- The tosser handles this process of distributing email
- and posts to the appropriate "pending" files for each
- network you are connected to. The tosser also handles
- the importation of incoming email and posts to the BBS,
- and the gating of posts between networks.
-
- Mail tosser operation is completely automatic and requires
- no special attention. Tossing may also, however, be invoked
- by command line switches or batch files called by external
- events to add flexibility. Please refer to the individual
- documentation for each network-specific interface for
- details on syntax and how this is accomplished. Such
- documentation is included in the zip file for each interface
- utility.
-
- Network-specific Interfaces
- ═══════════════════════════
- As of this moment, four basic network interface types
- may be used in conjunction with the VBBS multinet engine.
- These are as follows:
- VNET.EXE for VirtualNET-type networks (type 1)
- VWW4.EXE for WWIVnet-type networks (type 2)
- VUUCP.EXE for UUCP-type networks (type 3)
- VFIDO.EXE for FIDO-type networks (type 4)
-
- VBBS 6.12 Documentation--9-B-2
-
- These utilities may be downloaded from any VBBS support
- board and are accompanied by specific installation
- instructions.
-
- Please note that these utilities are not crippled in
- any manner, however, you should register VBBS within sixty
- (60) days to avoid an interruption of service. Failure to
- register will inactivate all interface utilities automatically,
- with the exception of VNET.EXE, after the 60-day period.
- To avoid any inconveniences, please register VBBS as soon as
- possible.
-
-
- VConfig
- ═══════
- The multinet configuration is done by running option 7, Network
- Configuration, in VConfig. From the net configuration menu, you
- simply choose which network you want to add, and enter the
- appropriate information. It is very important to remember after
- running option 7 to select option 3, Database Configuration,
- and run the Sort Databases and Compile Network functions found
- there.
-
- Answer.net Configuration
- ════════════════════════
- ANSWER.NET, an ordinary ascii text file, should be created
- and placed in your VBBS 'Data' subdirectory if you are to
- interface with other networks successfully. You must have
- answer.net set up properly for VBBS to be able to correctly
- identify incoming network calls. In many cases, the incoming
- network call will use a macro to identify itself. The
- answer.net file is used by the multinet engine to
- acknowledge the network macro, identify the network, and call
- up the proper network interface utility after connecting.
-
- Note that VirtualNET type networks do NOT need to be configured
- in ANSWER.NET since type 1 networks are automatic. However,
- to detect types 2 through 4, you must "program" ANSWER.NET to
- be able to identify the incoming network from the string it
- sends.
-
- ANSWER.NET uses only three simple one-character commands: ">",
- "!", and "?".
-
- ">" Sends a string. For example, >HELLO would transmit
- HELLO
-
- "!" Waits up to 2 seconds for a byte to come in
-
- "?" Compares received byte to ascii code values
- and calls up the appropriate network interface driver
-
- Here are some examples:
-
- ?78=2
- If received byte was 78 ("N"), then answer network #2 (WWIVnet)
- N N N N is the string that WWIVNet sends.
- VBBS 6.12 Documentation--9-B-3
- ?76=3
- If recevied byte was 76 ("L"), then answer network #3 (WWIVLInk).
- L L L L must be the string that WWIVLink sends and must be set
- up by your Link server using a macro.
-
- Here is an example ANSWER.NET, for a VBBS that is on WWIVnet
- only which you may use:
- !
- ?78=2
- ?32=2
-
- Here is an example you may use if you are on both WWIVnet and
- WWIVLink:
- !
- ?78=2
- ?32=2
- ?76=3
-
- Here is an example for a VBBS on USEnet:
- >UUCP
- !
- ?85=5
-
- Here is an example for a VBBS on USEnet, WWIVnet, and WWIVLink
- which may be used:
- >UUCP
- !
- ?78=2
- ?32=2
- ?76=3
- ?85=5
-
- Considerations for Wide-Area Networks
- ═════════════════════════════════════
- Because of VBBS' uniquely-designed multinet engine, starting
- your own new network is easier than ever before whether you
- are a business or an advanced system operator. Here are just
- a few things to consider if you are contemplating this:
-
- A) You will need to decide on what type of network software
- you want to use for your new network:
-
- VirtualNET type
- WWIVnet type
- FIDO type
- UUCP type
-
- While the multinet engine will easily handle any type above,
- remember that the simplest network to run operationally is a
- VirtualNET type network. This requires no special setup of
- the answer.net file or macro setup on the part of the server,
- has support for update utilities, and other advantages.
-
- B) You will need to select a name for your network.
-
- C) You will be responsible for maintaining your network, such
- as producing its bbslist or nodelist, establishing
- connections, nominating ACs, etc.
-
- VBBS 6.12 Documentation--9-B-4
-
- D) You should have the following thought out in advance:
-
- Network Policy and Goals
- Network Application
- Advertising
- Administration
-
- E) Update utilities
-
- Update utilities let you, as network coordinator send out
- BBSLISTs and SUBSLISTs for the maintenance of your network.
- Custom update utilities for VirtualNET type networks are
- available from the VBBS author. For more information on how
- to start a VirtualNET type network, please refer to the
- LOCALNET section of this document.
-
- F) Inclusion in NETWORKS.LST
-
- Here are the guidelines followed in handling networks.lst.
- There are NO exceptions to this policy and every new
- network must meet the criteria.
-
- NOTE: Applications will only be accepted from the NC of the
- network or their designate. Either the NC or the designate
- MUST be a registered VBBS sysop.
-
- 1. 10 new LocalNet slots 90-99 have been created.
- 2. Systems starting a network SHOULD use a localnet slot
- while the network is growing and getting established.
- 3. Once a network has 25 clients outside of their areacode,
- they can request formal recognition and addition to the
- Master Networks.lst file. They will then be assigned a
- permanent slot and the Networks List Co-Ordinator
- will do whatever he can to make the transition as fast and
- painless as possible, within reason. This includes help
- with mass/direct mailings to notify the current subscribers
- to your net and co-ordination of a switch date to your
- permanent slot.
- 4. Networks meeting the criteria (verifiable) of #3 will be
- immediately assigned a permanent slot. In accepting the
- permanent slot, the NC agrees to the following:
-
- A - Must write a Brief description of the network for inclusion
- in a text file distributed to all sysops monthly, listing the
- slot assigned, network name and a brief description of the
- network.
- B - Agrees to upload/send a zip file of what someone needs to
- join the network to 1@1803007 (Networks.lst Co-Cordinator)
- via VirtualNet, DirectMail (803-776-0323), Crash Fido Mail
- (1:376/142), or upload directly to my BBS. This will allow
- anyone interested in a network to always be able to get an
- application package from my board. This package should also
- include info on any restrictions the NC may specify as to
- accessing their net.
-
- VBBS 6.12 Documentation--9-B-5
-
- 5. Since Networks.LST is editable by anyone, and you can
- technically place your network in any slot not being used
- by your system, there stands a chance that people may not
- be able to join your net if you use the UUUCP slot and they
- are already in UUUCP. Crossed messages will not be allowed.
- In the event of a problem with two networks using the same
- slot which is causing problems, the Networks.lst co-ordinator
- will require one of the nets to move to another slot. The
- criteria used for this determination follows:
-
- A - Permanent Official Networks assigned a slot will always take
- precedence over one not officially recognized.
- B - Since having conflicts between Official Networks will be
- impossible, that leaves conflicts between localnet/empty
- slots to be resolved. The criteria for this will be:
- 1 - Number of Systems in Network
- 2 - Length of time Network in Operation.
- The object here is to make the transition to another slot as
- painless to the involved parties as possible. There will be
- no favoritism. The system which best meets the criteria will
- be allowed to keep the slot, the other will be asked to move.
- C - The Networks List Co-Ordinator will do all within reason and
- his power to assist someone in moving their network to a
- non-conflicting slot. After all, we are concerned here with
- the efficient operation of ALL networks and WANT them to
- succeed.
-
- Some other facts about the networks.lst file:
-
- 1 - There IS a limit to the number of the networks that can be
- in networks.lst.
- 2 - When editing networks.lst, do NOT leave any blank lines in
- it. This will cause problems. Delete all blank lines from
- the bottom.
- 3 - Each registered SYSTEM/SYSOP will only be allowed ONE
- permanent network in the official master list, IF/WHEN
- they meet the criteria above.
- 4 - There is a new sub which will be autosubscription called
- Networks.lst Information. We will answer questions and
- give out information on networks.lst and on how the system
- works.
-
- For additional information, contact:
-
- 1@1 VirtualNet
- Roland De Graaf
-
-
- .TOPIC:
- Extended Connects
- VBBS 6.12 Documentation--9-B-6
-
- EXTENDED CONNECTS
- ═════════════════
- VNet software is also capable of establishing special
- network connections to nodes who are not your official
- server. By establishing an extended connect, your bbs
- will be able to send and receive posts on autorequest
- subs, as well as e-mail. This ability comes in handy,
- for example, in an emergency when your regular
- VirtualNET server is down.
-
- To set up an extended connect, both you and the node you
- would like to connect to must set up an EXTEND.0 file in
- your main VBBS directory. It is important to make sure
- that the extend.0 file on both ends shows the extended
- connect going in both directions.
-
- For example, the entries below would set up an extended
- connect between @1 and @6160 if both @1 and @6160 had
- these entries in their extend.0 file:
-
- 1 6160
- 6160 1
-
- The concept is expandable also. Extend.0 is a list of all
- extended connects that you wish to take advantage of. On
- each line the first node is the system that has the extended
- connects and the others are the extended connects they use.
- For example, line 2 shows @6160 with extended connects @1,
- @1616001, and @6190.
-
- 1 6160
- 6160 1 1616001 6190
- 1616001 6160
- 6190 6160
-
- .TOPIC:
- Gateways
- VBBS 6.12 Documentation--9-B-7
-
- GATEWAYS
- ════════
- VNet also is able to handle email to other networks
- quite handily, even if your bbs is not actually on a
- network.
-
- For example, assume you wanted to send an email
- to someone on FIDOnet, but you're not actually on FIDOnet,
- but you are a member of VirtualNET.
-
- Your first step is to find a VirtualNET system that is
- also on FIDOnet and multinetworked.
-
- Once that is accomplished, email the sysop of that board
- and ask if you may use his system to gate email
- into the other network.
-
- If permission is granted, manually create a text file
- in your DATA directory, the filename should be GATEWAY.x
- where x is equal to the network id of the network you
- want to have a gateway to. In this example, since the
- target network is FIDOnet (Network ID = 4), we would create
- a GATEWAY.4 file in the DATA Directory. GATEWAY.4 will
- contain one line of ASCII text:
-
- @<system address>*<network number>
-
- <system address> is the node address of the gateway system.
- <network number> is the TRANSPORT NETWORK which will be used
- to gate the mail.
-
- For example, if you wanted a FIDOnet gateway to be
- @440 VirtualNET, you would make GATEWAY.4, with the line:
- @440*1
-
- Another example: If you want to email USEnet thru TechNET
- (Network ID = 8) system @1000, you would create a GATEWAY.5
- file (Network ID = 5 for USEnet), containing the line:
- @1000*8
-
- It should be noted that the TRANSPORT NETWORK must
- be of VirtualNET type. An email may, however, pass
- thru several gateways (no limit), if needed, to get
- it where you want it to go. This opens up some very
- powerful possibilities.
-
-
-
-